Device-Based Idle Mode Load Balancing

ABSTRACT

Concepts and technologies are described herein for device-based idle mode load balancing. According to one aspect disclosed herein, a mobile device can receive a cell information message that includes load information of a current camping cell on which the mobile device is currently camping and load information of at least one neighbor cell of a plurality of neighbor cells to the current camping cell. The mobile device can also obtain cell-type information of the current camping cell and cell-type information of the at least one neighbor cell. The mobile device can also determine a mobility state of the mobile device, and, based upon the load information of the current camping cell, the load information of the at least one neighbor cell, the cell-type information of the current camping cell, the cell-type information of the at least one neighbor cell, and the mobility state information, select a target camping cell.

TECHNICAL FIELD

The concepts and technologies disclosed herein generally relate to wireless telecommunications. More specifically, the concepts and technologies disclosed herein relate to device-based idle mode load balancing.

BACKGROUND

In recent years, mobile telecommunications carriers have experienced a dramatic increase in traffic on their networks, and this trend will likely continue. This increase in traffic has been caused in part by the increased adoption of smartphones and other devices that rely on mobile telecommunications networks, and the migration of many customers from utilizing landline telecommunication services to utilizing mobile telecommunication services for their communications needs. To meet the demands of higher traffic and to improve the end user experience, mobile telecommunications carriers are examining mechanisms by which to improve network efficiency, network capacity, and the end user experience, while keeping operational costs at a level conducive to maintaining competitive rates for the services they provide.

SUMMARY

Concepts and technologies are described herein for device-based idle mode load balancing. According to one aspect disclosed herein, a mobile device includes a processor and a memory. The memory can include computer-executable instructions that, when executed by the processor, cause the mobile device to perform operations. The operations can include receiving a cell information message that includes load information of a current camping cell on which the mobile device is currently camping and load information of at least one neighbor cell of a plurality of neighbor cells to the current camping cell. The operations can also include obtaining cell-type information of the current camping cell. The operations can also include obtaining cell-type information of the at least one neighbor cell. The operations can also include determining a mobility state of the mobile device, and, based upon the load information of the current camping cell, the load information of the at least one neighbor cell, the cell-type information of the current camping cell, the cell-type information of the at least one neighbor cell, and the mobility state information, selecting a target camping cell. The target cell can be a cell selected from the plurality of neighbor cells or can be the current camping cell.

According to another aspect disclosed herein, a computer-readable storage medium includes computer-executable instructions that, when executed by a processor of a mobile device, cause the mobile device to perform operations. The operations can include receiving a cell information message that includes load information of a current camping cell on which the mobile device is currently camping and load information of at least one neighbor cell of a plurality of neighbor cells to the current camping cell. The operations can also include obtaining cell-type information of the current camping cell. The operations can also include obtaining cell-type information of the at least one neighbor cell. The operations can also include determining a mobility state of the mobile device, and, based upon the load information of the current camping cell, the load information of the at least one neighbor cell, the cell-type information of the current camping cell, the cell-type information of the at least one neighbor cell, and the mobility state information, selecting a target camping cell. The target cell can be a cell selected from the plurality of neighbor cells or can be the current camping cell.

According to another aspect disclosed herein, a method can include receiving a cell information message that includes load information of a current camping cell on which the mobile device is currently camping and load information of at least one neighbor cell of a plurality of neighbor cells to the current camping cell. The method can also include obtaining cell-type information of the current camping cell. The method can also include obtaining cell-type information of the at least one neighbor cell. The method can also include determining a mobility state of the mobile device, and, based upon the load information of the current camping cell, the load information of the at least one neighbor cell, the cell-type information of the current camping cell, the cell-type information of the at least one neighbor cell, and the mobility state information, selecting a target camping cell. The target cell can be selected from the plurality of neighbor cells or can be the current camping cell.

In some embodiments, the cell-type information of the current camping cell and/or the at least one neighbor cell is obtained via the cell information message. In some other embodiments, the cell-type information of the current camping cell and/or the at least one neighbor cell is obtained based upon a determination made by the mobile device based at least in part upon Location Area Identity (“LAI”), Cell Identity (“CID”), Routing Area Identity (“RAI”), Tracking Area Identity (“TAI”), Physical Cell Identity (“PCI”), or some combination thereof.

It should be appreciated that the above-described subject matter may be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable storage medium. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating aspects of an illustrative operating environment for various concepts disclosed herein.

FIG. 2 is a block diagram illustrating aspects of a mobile device for idle mode load balancing, according to an illustrative embodiment.

FIG. 3 is a flow diagram illustrating aspects of a method for selecting a target camping cell, according to an illustrative embodiment.

FIG. 4 is a block diagram illustrating an example idle mode scenario for selecting a target camping cell based upon cell load, frequency band, and mobility state, according to an illustrative embodiment.

FIG. 5 is a flow diagram illustrating aspects of a method for selecting a target camping cell based upon cell load, frequency band, and mobility state, according to an illustrative embodiment.

FIG. 6 is a block diagram illustrating an example idle mode scenario for selecting a target camping cell based upon cell load, cell-type, radio access technology, and mobility state, according to an illustrative embodiment.

FIG. 7 is a flow diagram illustrating aspects of a method for selecting a target camping cell based upon cell load, cell-type, radio access technology, and mobility state, according to an illustrative embodiment.

FIGS. 8A-8B are block diagrams illustrating example idle mode scenarios for selecting a target camping cell based upon cell load, cell-type, and mobility state, according to illustrative embodiments.

FIG. 9 is a flow diagram illustrating aspects of a method for selecting a target camping cell based upon cell load, cell-type, and mobility state, according to an illustrative embodiment.

FIG. 10 is a block diagram illustrating an example idle mode scenario for selecting a target camping cell based upon cell load, cell-type, signal strength, and mobility state, according to an illustrative embodiment.

FIG. 11 is a flow diagram illustrating aspects of a method for selecting a target camping cell based upon cell load, cell-type, signal strength, and mobility state, according to an illustrative embodiment.

FIG. 12 is a block diagram illustrating an example computer system capable of implementing aspects of the embodiments presented herein.

FIG. 13 is a block diagram illustrating an example mobile device capable of implementing aspects of the embodiments disclosed herein.

DETAILED DESCRIPTION

Concepts and technologies are described herein for device-based idle mode load balancing. According to some of the concepts and technologies described herein, a mobile device performs idle mode load balancing across radio access technologies, including cellular and WI-FI technologies, across inter-frequencies within the same radio access technology, and across cell-types based upon local device information, such as mobility state, network load, and cell-types.

While the subject matter described herein may be presented, at times, in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, computer-executable instructions, and/or other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system, including hand-held devices, mobile devices, wireless devices, multiprocessor systems, distributed computing systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, routers, switches, other computing devices described herein, and the like.

In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments or examples. Referring now to the drawings, in which like numerals represent like elements throughout the several figures, example aspects of traffic steering across cell-types will be presented.

Referring now to FIG. 1, aspects of an illustrative operating environment 100 for various concepts disclosed herein will be described. It should be understood that the operating environment 100 and the various components thereof have been greatly simplified for purposes of discussion. Accordingly, additional or alternative components of the operating environment 100 can be made available without departing from the embodiments described herein.

The operating environment 100 shown in FIG. 1 includes a mobile device 102 that is configured to connect to and communicate with one or more radio access networks (“RANs”) for voice and/or data communications between the mobile device 102 and one or more other mobile devices, computers, servers, networking devices, and/or other networks (not shown). A RAN can include one or more cells having the same or different cells sizes, which may be represented by cell types. As used herein, a “cell” refers to a geographical area that is served by one or more base stations operating within a RAN. As used herein, a “base station” refers to a radio receiver and/or transmitter (collectively, transceiver) that is/are configured to provide a radio/air interface by which one or more mobile devices, such as the mobile device 102, can connect to a network. Accordingly, a base station is intended to encompass one or more base transceiver stations (“BTSs”), one or more Node Bs, one or more eNodeBs, and/or other networking nodes that are capable of providing a radio/air interface regardless of the technologies utilized to do so. A base station can be in communication with one or more antennas (not shown), each of which may be configured in accordance with any antenna design specifications to provide a physical interface for receiving and transmitting radio waves to/from a network.

A cell-type can be associated with certain dimensional characteristics that define the effective radio range of a cell. A cell-type can additionally represent the radio access technology (“RAT”) utilized by a cell. Cell types can include, but are not limited to, a macro cell-type, a metro cell-type, a femto cell-type, a pico cell-type, or a micro cell-type. Alternatively, cell-types can be proprietary, temporary, or ad-hoc in nature. An ad-hoc cell-type, for example, can include a mobile device, such as the mobile device 102, functioning as a “hotspot” for facilitating connectivity for other devices to another potentially larger cell.

The mobile device 102 may be a cellular phone, a feature phone, a smartphone, a mobile computing device, a tablet computing device, a portable television, a portable video game console, or any other computing device that is configured to connect to and communicate with one or more RANs via one or more radio access components. In some embodiments, the mobile device 102 includes an integrated or external radio access component that facilitates wireless communication with one or more RANs. The radio access component may be a cellular telephone that is in wired or wireless communication with the mobile device 102 to facilitate a tethered data connection to one or more RANs. Alternatively, the access component includes a wireless transceiver configured to send data to and receive data from one or more RANs and a universal serial bus (“USB”) or another communication interface for connection to the mobile device 102 so as to enable tethering. In any case, the mobile device 102 can wirelessly communicate with one or more RANs over a radio/air interface in accordance with one or more RATs. The mobile device 102 may also initiate, receive, and/or maintain voice calls with one or more other voice-enabled telecommunications devices such as other mobile devices or landline devices (not shown). The mobile device 102 may also exchange Short Message Service (“SMS”) messages, Multimedia Message Service (“MMS”) messages, email, and/or other messages with other devices (not shown).

As used herein, a RAN may operate in accordance with one or more mobile telecommunications standards including, but not limited to, Global System for Mobile communications (“GSM”), Code Division Multiple Access (“CDMA”) ONE, CDMA2000, Universal Mobile Telecommunications System (“UMTS”), Long-Term Evolution (“LTE”), Worldwide Interoperability for Microwave Access (“WiMAX”), other 802.XX technologies, and/or the like. A RAN can utilize various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, Time Division Multiple Access (“TDMA”), Frequency Division Multiple Access (“FDMA”), CDMA, wideband CDMA (“W-CDMA”), Orthogonal Frequency Division Multiplexing (“OFDM”), Single-Carrier FDMA (“SC-FDMA”), Space Division Multiple Access (“SDMA”), and/or the like to provide a radio/air interface to the mobile device 102. Data communications can be provided in part by a RAN using General Packet Radio Service (“GPRS”), Enhanced Data rates for Global Evolution (“EDGE”), the High-Speed Packet Access (“HSPA”) protocol family including High-Speed Downlink Packet Access (“HSDPA”), Enhanced Uplink (“EUL”) or otherwise termed High-Speed Uplink Packet Access (“HSUPA”), Evolved HSPA (“HSPA+”), LTE, and/or various other current and future wireless data access technologies. Moreover, a RAN may be a GSM RAN (“GRAN”), a GSM EDGE RAN (“GERAN”), a UMTS Terrestrial Radio Access Network (“UTRAN”), an E-UTRAN, any combination thereof, and/or the like.

A RAN can be part of one or more mobile telecommunications networks. As used herein, a mobile telecommunications network includes one or more RANs and a wireless wide area network (“WWAN”), which may, in turn, include one or more core networks such as a circuit-switched core network (“CS CN”), a packet-switched core network (“PS CN”), and/or an IP multimedia subsystem (“IMS”) core network. The WWAN can utilize one or more mobile telecommunications technologies, such as those described above, to provide voice and/or data services via one or more RANs to one or more radio components of one or more mobile devices of mobile device 102. Moreover, a mobile telecommunications network can provide a connection to the Internet or other WAN so that the mobile device 102 can access Internet content such as Websites, streaming media, online video games, downloadable content, and the like.

The mobile device 102 is configured to receive a cell information message 104, which can include local cell information 106 collected by a base station 108 that is operating within a cell 110 of a RAN. The local cell information 106 can include cell-type information of the cell 110. The local cell information 106 can also include cell load information of the cell 110. The cell information message 104 can additionally include at least a portion of cell information 112A-112N (hereinafter, at times, referred to herein collectively or generically as “cell information 112”) collected by one or more other base stations 114A-114N (hereinafter, at times, referred to herein collectively or generically as “other base stations 114”) that operate in corresponding cells 116A-116N (hereinafter, at times, referred to herein collectively or generically as “other cells 116”) of the same RAN as the cell 110 or one or more other RANs. The cell information 112 can include cell-type information of one or more of the other cells 116. The cell information 112 can also include cell load information of one or more of the other cells 116.

The other cells 116 may be neighbor cells to the cell 110, and one or more of the other cells 116 may overlap with the cell 110 and/or each other. Moreover, the cell 110 and the other cells 116 may be of any cell-type or any combination of cell types. As the mobile device 102 moves, the mobile device 102 can select one of the other cells 116 as the target camping cell. Alternatively, the mobile device 102 can select the cell 110 as the target camping cell.

The mobile device 102 can operate in an idle mode or a connected mode. When the mobile device 102 is in the idle mode, the cell 110 is a current camping cell for the mobile device 102. In this case, the other cells 116 may be considered by the mobile device 102 for selection as potential target camping cells. Alternatively, the cell 110 can be selected by the mobile device 102 as the target camping cell. Examples of the mobile device 102 operating in an idle mode are illustrated and described below with reference to FIGS. 3-11.

The mobile device 102 utilizes information contained within the cell information message 104 at least in part to select a neighbor cell or the current camping cell as the target camping cell. The mobile device 102 can also utilize local device information such as, but not limited to, mobility state information, performance measurement information, battery utilization information, channel quality information, and/or a user override selection, in selecting the target camping cell, as will be described in greater detail below with reference to FIG. 2.

Cell-type information can identify a cell as being of a particular cell type. The cell information message 104 can include an explicit specification of a cell-type of one or more cells. For example, the cell information message 104 may include text that explicitly names the cell-type for a given cell. As another example, the cell information message 104 may include a code or identifier by which the mobile device 102 can ascertain the cell-type of one or more cells. In this example, the mobile device 102 may have a table or other data structure by which to cross-reference cell-type codes or identifiers with cell-types.

The cell information message 104 can include any message that is capable of being sent to the mobile device 102 from a base station over a radio/air interface. The cell information message 104 can be sent to the mobile device 102 using any physical, transport, and/or logical channels. These channel types are generally known and therefore are not described in greater detail herein.

In some embodiments, the cell information message 104 is a System Information Block (“SIB”). In some other embodiments, the cell information message 104 is included in a SIB that contains other information. The SIB may be a new SIB configured to include cell-type information for one or more cells. Alternatively, the SIB may be an existing SIB that has been modified to include cell-type information for one or more cells.

In some embodiments, the cell information message 104 is an SMS message. In these embodiments, the base station 108 can send the cell information message 104 to the mobile device 102, and potentially to one or more other mobile devices that are connected to the base station 108 or otherwise operating within the cell 110, via SMS Cell Broadcast (“SMS-CB”). Alternatively, in these embodiments, the base station 108 can send the cell information message 104 to the mobile device 102 via SMS Peer-to-Peer (“SMPP”). The cell information message 104 may be sent to the mobile device 102 via other messaging services including, but not limited to, MMS, Wireless Application Protocol (“WAP”) push message, Unstructured Supplementary Service Data (“USSD”), or any combination thereof. It should be understood that network elements, such as Short Message Service Centers (“SMSCs”), Multimedia Message Service Centers (“MMSCs”), WAP servers, USSD servers, and the like, that support the aforementioned messaging services are not illustrated merely for ease of description.

Cell-type information can be conveyed to the mobile device 102 using existing information such as, but not limited to, Location Area Identity (“LAI”), Cell Identity (“CID”), Routing Area Identity (“RAI”), Tracking Area Identity (“TAI”), Physical Cell Identity (“PCI”), or some combination thereof. In these embodiments, the mobile device 102 can use one of these identities, or some combination thereof, to determine the cell-type of one or more cells, for example, utilizing a table or other data structure stored on or otherwise accessible by the mobile device 102.

A cell-type can be associated with a particular identity or range of identities of one or more of the above identities. For example, an ID range of 100-49,999 may be assigned to macro cells, an ID range of 50,000-200,000 may be assigned to metro cells, and so on. The mobile device 102 can be configured to ascertain LAI, CID, RAI, TAI, or some combination thereof, and determine a cell-type for the cell(s) associated with one or more of these IDs.

In some embodiments, cell-type information of a current camping cell and/or at least one neighbor cell is obtained by the mobile device 102 via the cell information message 104. In some other embodiments, the cell-type information of the current camping cell and/or at least one neighbor cell is obtained based upon a determination made by the mobile device based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

In the illustrated example, the mobile device 102 receives the cell information message 104 from the base station 108. Alternatively or additionally, the mobile device 102 can receive one or more cell information messages from any number of base stations such as one or more of the other base stations 114. Also in the illustrated example, the cell information message 104 includes the local cell information 106 and the cell information 112. However, it is contemplated that the cell information message 104 may include only the local cell information 106, only the cell information 112A, only the cell information 112B, only the cell information 112N, or any combination thereof.

In some embodiments, the base station 108 learns cell-type information and/or load information from one or more neighbor base stations, which may include one or more of the other base stations 114. The base station 108 may learn cell-type information and/or the load information via a self-organizing network (“SON”) feature such as provided by 3^(rd) Generation Partnership Project (“3GPP”) and/or New Generation Mobile Networks (“NGMN”). In particular, the base station 108 can utilize the Automatic Neighbor Relation (“ANR”) detection feature of LTE to detect one or more of the other base stations 114 and collect the cell information 112 therefrom. Other mechanisms by which the base station 108 can learn load information of one or more neighboring cells are contemplated.

In some embodiments, load information includes historic load information. Historic load information is used herein to describe load information obtained based upon load experienced by the base station 108 and/or one or more of the other base stations 114 in the past or otherwise in non-real-time. In some embodiments, historic load information is utilized by the mobile device 102 to identify one or more load trends over a specified period of time. This trending load information can be useful to the mobile device 102 to predict times during which load is favorable or not to support communications between the mobile device 102 and one or more cells.

In some embodiments, load information additionally or alternatively includes current load information. Current load information is used herein to describe load information that is obtained based upon a load experienced by the base station 108 and/or one or more of the other base stations 114 in real-time or near real-time. Real-time, in this context, is the actual time during which a load is experienced by the base station 108 and/or one or more of the other base stations 114. Near real-time, in this context, is the actual time during which a network load is experienced by the base station 108 and/or one or more of the other base stations 114 plus a delay on the order of microseconds or milliseconds, for example.

What constitutes near-real time load information versus historic load information can be defined by a service provider providing service via the base station 108 and/or one or more of the other base stations 114. It should be understood that real-time load information associated with a real-time load of the base station 108 and/or one or more of the other base stations 114, and near real-time network load information associated with a near real-time network load of the base station 108 and/or one or more of the other base stations 114 might be received by the mobile device 102 with delay caused by latency and/or other network phenomena. Moreover, this delay may increase with the additional time needed to generate the cell information message 104 that includes the local cell information 106 and/or the load information 122, and send the cell information message 104 to the mobile device 102.

In some embodiments, load information includes a number of active devices (e.g., devices currently engaged in a call or data session). In some other embodiments, load information includes a number of idle devices (e.g., devices currently camped on a given cell). It is contemplated that load information can include both a number of active devices and a number of idle devices. In other words, load information can include active load information and idle load information. The mobile device 102 can utilize the active load information and/or the idle load information for selecting a target camping cell or selecting a target camping cell.

In some embodiments, a cell includes a base station that operates utilizing multiple frequency bands. The mobile device 102 can select a frequency band based upon, for example, the current speed of the mobile device 102. For example, if the base station 108 provides a 700 megahertz (“MHz”) frequency band and an AWS frequency band, the mobile device 102 might select the 700 MHz band if the mobile device 102 is moving at a relatively high speed, such as 55 miles per hour, because of the better performance offered by the 700 MHz frequency band in such scenarios.

It should be understood that some implementations of the operating environment 100 may include additional functionality or include less functionality than described above. Thus, the illustrated embodiment should be understood as being illustrative, and should not be construed as being limiting in any way.

In some situations, a mobile device might move into and out of a cell, thereby causing a ping-pong effect. In order to avoid this situation, the mobile device can use one or more of the following approaches to decide whether and/or when to camp on a selected cell. In a first approach, the mobile device can back-off a random period of time (0, t), where t is the time interval between two SIB messages for load broadcast. In a second approach, a probability of action, p, is utilized, wherein p is the function of in-balance factor between the current camping cell and one or more neighbor candidate cells. The aforementioned factors can be utilized alone, in combination, or in combination with other means, such as, for example, changing the cell re-selection priority to a set of mobile devices when the radio resource control (“RRC”) connection is released.

Turning now to FIG. 2, a block diagram illustrating additional aspects of the mobile device 102 will be described, according to an illustrative embodiment. In the illustrated embodiment, the mobile device 102 is configured to receive cell-type information 200 and cell load information 202, and utilize at least some of this information to determine to which cell the mobile device 102 should connect. The cell-type information 200 can include, for example, the cell-type of one or more cells, such as the cell 110 and/or one or more of the other cells 116 shown in FIG. 1. The cell load information 202 can include, for example, the cell load of one or more cells, such as the cell 110 and/or one or more of the other cells 116.

The illustrated mobile device 102 also includes an operating system 204, a network connection manager 206, a network decision engine 208, one or more radio access components 210, and local device information 212. The operating system 204 is a program for controlling the operation of the mobile device 102. The operating system 204 can include a member of the SYMBIAN OS family of operating systems from SYMBIAN LIMITED, a member of the WINDOWS MOBILE OS and/or WINDOWS PHONE OS families of operating systems from MICROSOFT CORPORATION, a member of the PALM WEBOS family of operating systems from HEWLETT PACKARD CORPORATION, a member of the BLACKBERRY OS family of operating systems from RESEARCH IN MOTION LIMITED, a member of the IOS family of operating systems from APPLE INC., a member of the ANDROID OS family of operating systems from GOOGLE INC., and/or other operating systems. These operating systems are merely illustrative of some contemplated operating systems that may be used in accordance with various embodiments of the concepts and technologies described herein and therefore should not be construed as being limiting in any way.

The network connection manager 206 can be configured to manage all or a portion of the network connections available to the mobile device 102 at a given time, including, for example, connections established via one or more one or more cellular radios of the mobile device 102 such as one or more of the radio access components 210. In some embodiments, the network connection manager 206 is included as part of the operating system 204 and/or another application stored on the mobile device 102 such as the network decision engine 208.

The network decision engine 208 utilizes the cell-type information 200, the load information 202, the local device information 212, frequency band information, RAT type, or any combination thereof, to make a determination as to which cell the mobile device 102 should select as the target camping cell. In some embodiments, the network decision engine 208 is an application program that includes computer-executable instructions that, when executed by one or more processors of the mobile device 102, cause the mobile device 102 to analyze the cell-type information 200, the load information 202, the local device information 212, frequency band information, RAT type, alone or in any combination to select a cell, and to instruct the mobile device 102, and more particularly, the network connection manager 206, to establish communication with a base station operating within the selected cell.

In some embodiments, the network decision engine 208 includes or accesses “AND” network selection logic, whereby the network decision engine 208 can determine to select a combination of two or more RATs. For example, the network decision engine 208 can determine to select an LTE macro cell and a WI-FI access point to camp on, and can determine which of these RATs to utilize when a connection is needed. A combination of RATs can be useful for load balancing according to application specific requirements, which could be more or less sensitive to the limitations of WI-FI versus cellular.

In some embodiments, the network decision engine 208 utilizes information additional to that which is described above to select a cell. This information can include, for example, one or more policies and/or one or more user profiles. As used herein, the term “policy” refers to one or more settings, one or more configurations, one or more rules, and/or the like that define, at least in part, one or more courses or methods of action in light of one or more conditions to be used in a determination made by the mobile device 102 regarding to which cell the mobile device 102 should connect. In some embodiments, a policy includes one or more rules that specify one or more if-then conditions by which to handle a particular situation, such as redirecting network traffic based upon load experienced by the base station 108 and/or one or more of the other base stations 114 and that is reported to the mobile device 102 in the cell information message 104. In some other embodiments, a policy includes one or more matrices of cause and effect conditions, tables of actions, or the like for responding to or otherwise dealing with certain stimuli, such as network conditions evidenced by the local cell information 106, the cell information 112, and/or other stimuli.

As used herein, the term “user profile” refers to a collection of data associated with a user that accesses one or more RANs via a device such as the mobile device 102. A user in this context refers to an individual or other entity. A user profile can define information regarding a service agreement between a user and one or more service providers that provide a service, at least in part, via one or more RANs. The service agreement may include terms of service for pre-paid and/or post-paid service. The service agreement may include terms of roaming agreements between two or more mobile telecommunications carriers. The service agreement may define a service tier for the user. A service tier may establish a priority for a user in regard to utilizing network resources to connect to one or more RANs via the mobile device 102.

The illustrated local device information 212 includes mobility state information 214, one or more user rules 216, one or more applications 218, performance measurement information 220, battery utilization information 222, and channel quality information 224. These types of local device information are merely illustrative of some contemplated information that may be used in accordance with various embodiments of the concepts and technologies described herein for selecting a cell and therefore should not be construed as being limiting in any way.

The mobility state information 214 can include the speed at which the mobile device 102 is currently moving, a movement pattern of the mobile device 102, and/or any other information associated with movement or non-movement of the mobile device 102. The mobility state information 210 may be obtained by an accelerometer, Global Positioning System (“GPS”) component, and/or other motion sensor or component of the mobile device 102. The mobility state information 214 can be utilized by the network decision engine 208 to determine if it is appropriate for the mobile device 102 to connect to a network, or a particular cell thereof, given the movement or non-movement of the mobile device 102. For example, if the mobility state information 214 indicates that the mobile device 102 is moving at 60 miles per hour and a metro cell is available to the mobile device 102, the network decision engine 208 can determine to forgo connecting to the metro cell based upon the relatively fast movement of the mobile device 102 and the prediction that the mobile device 102 will not be within range of a base station operating within the metro cell for a sufficient amount of time to handle voice and/or data communications between the mobile device 102 and the metro cell. Alternatively, for example, if the mobility state information 214 indicates that the mobile device 102 is stationary and a metro cell is available to the mobile device 102, the device-based network decision engine 208 can determine to connect to the metro cell based upon the stationary state of the mobile device 102 and the prediction that the mobile device 102 will be within range of the metro cell for a sufficient amount of time to handle voice and/or data communications between the mobile device 102 and the metro cell. The mobility state information 214 can also be used to select a RAT or a particular frequency band of a RAT when multiple frequency bands are available.

The user rule(s) 216 can include rules specified by or for a user of the mobile device 102 regarding cell selections. For example, a user rule may specify an override selection of a cell or a particular cell-type that should be selected if the particular cell or cell-type is available. An override selection can be conditional. In some embodiments, the user rule(s) 216 are overridden by one or more policies.

The application(s) 218 can include an indication of one or more applications that are currently utilizing processing and/or memory resources of the mobile device 102. In some embodiments, information regarding the application(s) 218 is received by the network decision engine 208 from the operating system 204, and more particularly, a resource management function of the operating system 204. The network decision engine 208 can utilize the application(s) 218 to select a cell within a network that is capable of voice and/or data communications originating from or directed to the application(s) 218. For example, if a video streaming application is active on the mobile device 102, the network decision engine 208 can determine to select a cell within a network that has sufficient bandwidth resources to support streaming video to the mobile device 102. The application(s) 218 can additionally or alternatively include an indication of one or more application that are currently installed on the mobile device 102.

The performance measurement information 220 can include signal strength, round-trip time (“RTT”), throughput, latency, and/or other performance measurements obtained by the mobile device 102. In some embodiments, the mobile device 102 is configured to perform one or more tests to obtain the performance measurement information 220. The tests may be performed by standalone test applications executing on the mobile device 102, the operating system 200, the network decision engine 208, and/or the network connection manager 206. By way of example and not limitation, illustrative tests include throughput tests, latency tests, call tests, SMS tests, multiple radio access bearer (“mRAB”) tests (e.g., simultaneous voice and data tests), voice over Internet protocol (“VoIP”), video mean opinion score (“MOS”), or idle tests.

The battery utilization information 222 can include information such as, but not limited to, a current, a voltage, a temperature, a percentage of battery used, a percentage of battery remaining, a battery condition, a remaining time, and a remaining capacity (e.g., in watt hours). In some embodiments, the battery utilization information 222 is obtained from a battery gauge of the mobile device 102 that is configured to measure the effect of a battery's discharge rate, temperature, age, and/or other factor to predict the remaining life within a certain percentage of error.

The channel quality information 224 can include a channel quality indicator (“CQI”) or other measurement that is indicative of the quality of a given channel over which the mobile device 102 can communicate. In some embodiments, a CQI is calculated based at least in part upon the channel quality information 224 includes a signal-to-noise (“SNR”), a signal-to-interference plus noise ratio (“SING”), a signal-to-noise plus distortion ratio (“SNDR”), and/or the like for a given channel.

Turning now to FIG. 3, a flow diagram illustrating aspects of a method 300 for selecting a target camping cell will be described, according to an illustrative embodiment. It should be understood that the operations of the illustrative methods disclosed herein are not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be combined, separated, added, omitted, modified, and/or performed simultaneously or in another order without departing from the scope of the subject disclosure.

It also should be understood that the illustrated methods can be ended at any time and need not be performed in their entirety. Some or all operations of the methods, and/or substantially equivalent operations, can be performed by execution of computer-executable instructions included on a computer-readable storage media, as defined below. The term “computer-executable instructions,” and variants thereof, as used in the description and claims, is used expansively herein to include routines, application programs, software, application modules, program modules, components, data structures, algorithms, and the like. Computer-executable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, distributed computing systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like. As used herein, “cause a processor to perform operations” includes causing a processor of a computing system or computing device such as the mobile device 102, the base station 108, one or more of the other base stations 114, or other computing systems or devices described herein, to perform one or more operations of the operations and/or causing the processor to direct other components of the computing system or device to perform one or more of the operations.

Thus, it should be appreciated that the logical operations described herein may be implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.

The method 300 begins and proceeds to operation 302, wherein the mobile device 102 obtains cell-type information of a cell on which the mobile device 102 is currently camping (hereinafter referred to as “current camping cell”). In some embodiments, the mobile device 102 obtains the cell-type information of the current camping cell via the cell information message 104. In some other embodiments, the mobile device 102 obtains the cell-type information of the current camping cell based upon a determination made by the mobile device 102 based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

From operation 302, the method 300 proceeds to operation 304, wherein the mobile device 102 obtains cell-type information of one or more neighbor cells to the current camping cell. In some embodiments, the mobile device 102 obtains the cell-type information of the neighbor cell(s) via the cell information message 104. In some other embodiments, the mobile device 102 obtains the cell-type information of the neighbor cell(s) based upon a determination made by the mobile device 102 based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

From operation 304, the method 300 proceeds to operation 306, wherein the mobile device 102 receives load information of the current camping cell and the neighbor cell(s). From operation 306, the method 300 proceeds to operation 308, wherein the mobile device 102 receive load information of one or more available WI-FI networks.

From operation 308, the method 300 proceeds to operation 310, wherein the mobile device 102 determines a mobility state of the mobile device 102. From operation 308, the method 300 proceeds to operation 312, wherein the mobile device 102 selects a target camping cell based upon the cell-type information, the load information, and the mobility state of the mobile device 102. The mobile device 102 can select the current camping cell or one of the neighbor cells as the target camping cell. From operation 312, the method 300 proceeds to operation 314, wherein the method 300 may end.

Turning now to FIG. 4, a block diagram illustrating an example idle mode scenario 400 for selecting a target camping cell based upon cell load, frequency band, and mobility state will be described, according to an illustrative embodiment. In the example idle mode scenario 400, the mobile device 102 receives load information 402 from a current camping base station 404 operating within a current camping cell 406. In this example, the current camping cell 406 is capable of providing service to the mobile device 102 via two frequencies. As such, the load information 402 includes the cell load of two logical cells (“cell 1, cell 2”).

The mobile device 102 is moving away from the current camping cell 406 at 55 miles per hour. Since the mobile device 102 is moving at such speed, and given the frequency bands of 700 MHz and AWS provided by the current camping base station 404, the mobile device 102 can determine that 700 MHz frequency band provides better performance. Accordingly, the mobile device 102 can select cell 1, which is operating on the 700 MHz frequency band, as the target camping cell.

Turning now to FIG. 5, a flow diagram illustrating aspects of a method 500 for selecting a target camping cell based upon cell load, frequency band, and mobility state will be described, according to an illustrative embodiment. The method 500 is described with additional reference to the example idle mode scenario 400 illustrated and described with reference to FIG. 4.

The method 500 begins and proceeds to operation 502, wherein the mobile device 102 receives load information for multiple frequencies provided by a current camping cell. From operation 502, the method 500 proceeds to operation 504, wherein the mobile device 102 determines a mobility state of the mobile device 102. From operation 504, the method 500 proceeds to operation 506, wherein the mobile device 102 selects a target camping cell based upon the load information, the available frequency bands, and the mobility state of the mobile device 102. From operation 506, the method 500 proceeds to operation 508, wherein the method 500 may end.

Turning now to FIG. 6, a block diagram illustrating an example idle mode scenario 600 for selecting a target camping cell based upon cell load, cell-type, RAT type, and mobility state will be described, according to an illustrative embodiment. In the example idle mode scenario 600, the mobile device 102 receives load information 602 from a current camping base station 604 operating within a current camping cell 606. In this example, the current camping cell 606 is capable of providing service to the mobile device 102 via two RATs—UMTS and LTE. As such, the load information 602 includes the cell load of two logical cells (“cell 1, cell 2”). Also in the example idle mode scenario 600, the mobile device 102 receives WI-FI load information 608 from a WI-FI access point 610.

The mobile device 102 is moving away from the current camping cell 606 at 35 miles per hour. Since the mobile device 102 is moving at such speed, and given the RATs provided by the current camping base station 606 and the WI-FI access point 610, the mobile device 102 can select cell 1, which provides UMTS service, as being best-suited for the given conditions. WI-FI is not suitable in the example idle mode scenario 600 because of the speed at which the mobile device 102 is moving.

Turning now to FIG. 7, a flow diagram illustrating aspects of a method 700 for selecting a target camping cell based upon cell load, cell-type, RAT type, and mobility state will be described, according to an illustrative embodiment. The method 700 is described with additional reference to the example idle mode scenario 600 illustrated and described with reference to FIG. 6.

The method 700 begins and proceeds to operation 702, wherein the mobile device 102 receives load information for multiple RATs provided by the current camping cell. From operation 702, the method 700 proceeds to operation 704, wherein the mobile device 102 receives load information of one or more available WI-FI networks. From operation 704, the method 700 proceeds to operation 706, wherein the mobile device 102 obtains cell-type information of the current camping cell. In some embodiments, the mobile device 102 obtains the cell-type information of the current camping cell via the cell information message 104. In some other embodiments, the mobile device 102 obtains the cell-type information of the current camping cell based upon a determination made by the mobile device 102 based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

From operation 706, the method 700 proceeds to operation 708, wherein the mobile device 102 determines a mobility state of the mobile device 102. From operation 708, the method 700 proceeds to operation 710, wherein the mobile device 102 selects a target camping cell based upon the load information, cell-type, the RAT type, and the mobility state of the mobile device 102. From operation 710, the method 700 proceeds to operation 712, wherein the method 700 may end.

FIGS. 8A-8B are block diagrams illustrating example idle mode scenarios 800A-800B for selecting a target camping cell based upon cell load, cell-type, and mobility state, according to illustrative embodiments. Turning first to FIG. 8A, the mobile device 102 receives load information 802 from a current camping base station 804 operating within a current camping cell 806 (“cell 2”) on which the mobile device 102 is currently camped. The load information 802 includes the cell load of the current camping cell 806 and two neighbor cells—a metro cell 808 (“cell 1”) and a macro cell 810 (“cell 3”). In the illustrated example, the current camping cell 806, the metro cell 808, and the macro cell 810 are all being controlled by a radio network controller (“RNC”) 814. In other implementations, the current camping cell 806, the metro cell 808, and the macro cell 810 may be controlled by any number of RNCs or like network elements depending upon the RATs utilized by the cells.

The mobile device 102 is moving from the current camping cell 806 towards the metro cell 808 and the macro cell 810 at 1 mile per hour. Since the mobile device 102 is moving at such speed and given the radio range provided by the metro cell-type, the mobile device 102 can determine that the metro cell 308 is a good candidate for the target camping cell. The macro cell 310, on the other hand, has sufficient radio range as specified by its macro cell-type, but the load information 802 indicates the load of the metro cell 808 is low relative to its capacity whereas the load of the macro cell 810 is medium relative to its capacity. Therefore the mobile device 102 can select the metro cell 808 as the target camping cell. In this example, given the slow speed of the mobile device 102, the metro cell 808 or the macro cell 810 are qualified camping cell candidates, but the lower load of the metro cell 808 might facilitate a better overall user experience, and so is selected as the target camping cell.

Turning now to FIG. 8B, the mobile device 102 is moving from the current camping cell 806 towards the metro cell 808 and the macro cell 810 at 35 miles per hour. Since the mobile device 102 is moving at such speed and given the radio range provided by the metro cell-type, the mobile device 102 can determine that the metro cell 808 is not a good candidate for the target camping cell. The macro cell 810, on the other hand, has sufficient radio range as specified by its macro cell-type, and therefore the mobile device 102 can select the macro cell 310 as the target camping cell.

Turning now to FIG. 9, a flow diagram illustrating aspects of a method 900 for selecting a target camping cell based upon cell load, cell-type, and mobility state will be described, according to an illustrative embodiment. The method 900 is described with additional reference to the example idle mode scenarios 800A-800B illustrated and described with reference to FIG. 8.

The method 900 begins and proceeds to operation 902, wherein the mobile device 102 obtains cell-type information of the current camping cell. In some embodiments, the mobile device 102 obtains the cell-type information of the current camping cell via the cell information message 104. In some other embodiments, the mobile device 102 obtains the cell-type information of the current camping cell based upon a determination made by the mobile device 102 based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

From operation 902, the method 900 proceeds to operation 904, wherein the mobile device 102 receives cell-type information of one or more neighbor cells to the current camping cell. In some embodiments, the mobile device 102 obtains the cell-type information of the neighbor cell(s) via the cell information message 104. In some other embodiments, the mobile device 102 obtains the cell-type information of the neighbor cell(s) based upon a determination made by the mobile device 102 based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

From operation 904, the method 900 proceeds to operation 906, wherein the mobile device 102 receives load information of the current camping cell and the neighbor cell(s). From operation 906, the method 900 proceeds to operation 908, wherein the mobile device 102 determines a mobility state of the mobile device 102. From operation 908, the method 900 proceeds to operation 910, wherein the mobile device 102 selects a target camping cell based upon the cell-type information, the load information, and the mobility state of the mobile device 102. From operation 910, the method 900 proceeds to operation 912, wherein the method 900 may end.

Turning now to FIG. 10, a block diagram illustrating an example idle mode scenario 1000 for selecting a target camping cell based upon cell load, cell-type, signal strength, and mobility state will be described, according to an illustrative embodiment. In the example idle mode scenario 1000, the mobile device 102 receives load information 1002 from a current camping base station 1004 operating within a current camping cell 1006 (“cell 2”) on which the mobile device 102 is currently camped. The load information 1002 includes the cell load of the current camping cell 1006 and two neighbor cells—a metro cell 1008 (“cell 1”) and a macro cell 1010 (“cell 3”). In the illustrated example, the current camping cell 1006, the metro cell 1008, and the macro cell 1010 are all being controlled by an RNC 1014. In other implementations, the current camping cell 1006, the metro cell 1008, and the macro cell 1010 may be controlled by any number of RNCs or like network elements depending upon the RATs utilized by the cells.

The mobile device 102 is moving from the current camping cell 1006 towards the metro cell 1008 and the macro cell 1010 at 35 miles per hour. Since the mobile device 102 is moving at such speed and given the radio range provided by the metro cell-type, the mobile device 102 can determine that the metro cell 1008 is not a good candidate for the target camping cell. The macro cell 310, on the other hand, has sufficient radio range as specified by its macro cell-type and is capable of additional load as specified by the load information 1002, but the signal strength of the macro 310 is low. Therefore, the mobile device 102 can select the current camping cell 1006 to remain the target camping cell.

Turning now to FIG. 11, a flow diagram illustrating aspects of a method 1100 for selecting a target camping cell based upon cell load, cell-type, signal strength, and mobility state will be described, according to an illustrative embodiment. The method 1100 is described with additional reference to the example idle mode scenario 1000 illustrated and described with reference to FIG. 10.

The method 1100 begins and proceeds to operation 1102, wherein the mobile device 102 obtains cell-type information of the current camping cell. In some embodiments, the mobile device 102 obtains the cell-type information of the current camping cell via the cell information message 104. In some other embodiments, the mobile device 102 obtains the cell-type information of the current camping cell based upon a determination made by the mobile device 102 based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

From operation 1102, the method 1100 proceeds to operation 1104, wherein the mobile device 102 receives cell-type information of one or more neighbor cells to the current camping cell. In some embodiments, the mobile device 102 obtains the cell-type information of the current camping cell via the cell information message 104. In some other embodiments, the mobile device 102 obtains the cell-type information of the current camping cell based upon a determination made by the mobile device 102 based at least in part upon LAI, CID, RAI, TAI, PCI, or some combination thereof.

From operation 1104, the method 1100 proceeds to operation 1106, wherein the mobile device 102 receives load information of the current camping cell and the neighbor cell(s). From operation 1106, the method 1100 proceeds to operation 108, wherein the mobile device 102 determines a mobility state of the mobile device 102. From operation 1108, the method 1100 proceeds to operation 1110, wherein the mobile device 102 determines the received signal strength from the current camping cell and the neighbor cell(s). From operation 1110, the method 1100 proceeds to operation 1112, wherein the mobile device 102 selects a target camping cell based upon the cell-type information, the load information, the received signal strength, and the mobility state of the mobile device 102. From operation 1112, the method 1100 proceeds to operation 1114, wherein the method 1100 may end.

FIG. 12 is a block diagram illustrating a computer system 1200 configured to perform various operations disclosed herein. The computer system 1200 includes a processing unit 1202, a memory 1204, one or more user interface devices 1206, one or more input/output (“I/O”) devices 1208, and one or more network devices 1210, each of which is operatively connected to a system bus 1212. The system bus 1212 enables bi-directional communication between the processing unit 1202, the memory 1204, the user interface devices 1206, the I/O devices 1208, and the network devices 1210. In some embodiments, the base station 108 and/or one or more of the other base stations 114 is configured, at least in part, like the computer system 1200. It should be understood, however, that the base station 108 and/or one or more of the other base stations 114 may include additional functionality or include less functionality than now described.

The processing unit 1202 may be a standard central processor that performs arithmetic and logical operations, a more specific purpose programmable logic controller (“PLC”), a programmable gate array, or other type of processor known to those skilled in the art and suitable for controlling the operation of the computer system 1200. Processing units are generally known, and therefore are not described in further detail herein.

The memory 1204 communicates with the processing unit 1202 via the system bus 1212. In some embodiments, the memory 1204 is operatively connected to a memory controller (not shown) that enables communication with the processing unit 1202 via the system bus 1212. The illustrated memory 1204 includes an operating system 1214 and one or more applications 1216.

The operating system 1214 can include, but is not limited to, members of the WINDOWS, WINDOWS CE, WINDOWS MOBILE, and/or WINDOWS PHONE families of operating systems from MICROSOFT CORPORATION, the LINUX family of operating systems, the SYMBIAN family of operating systems from SYMBIAN LIMITED, the BREW family of operating systems from QUALCOMM CORPORATION, the MAC OS and/or iOS families of operating systems from APPLE INC., the FREEBSD family of operating systems, the SOLARIS family of operating systems from ORACLE CORPORATION, other operating systems such as proprietary operating systems, and the like.

The user interface devices 1206 may include one or more devices with which a user accesses the computer system 1200. The user interface devices 1206 may include, but are not limited to, computers, servers, personal digital assistants, telephones (e.g., cellular, IP, or landline), or any suitable computing devices. The I/O devices 1208 enable a user to interface with the program modules. In one embodiment, the I/O devices 1208 are operatively connected to an I/O controller (not shown) that enables communication with the processing unit 1202 via the system bus 1212. The I/O devices 1208 may include one or more input devices, such as, but not limited to, a keyboard, a mouse, or an electronic stylus. Further, the I/O devices 1208 may include one or more output devices, such as, but not limited to, a display screen or a printer.

The network devices 1210 enable the computer system 1200 to communicate with other networks or remote systems via a network 1218. Examples of the network devices 1210 include, but are not limited to, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface, a bridge, a router, or a network card. The network 1218 may include a wireless network such as, but not limited to, a WLAN such as a WI-FI network, a WWAN, a wireless PAN (“WPAN”) such as BLUETOOTH, or a wireless MAN (“WMAN”). Alternatively, the network 1218 may be a wired network such as, but not limited to, a WAN such as the Internet, a LAN such as the Ethernet, a wired PAN, or a wired MAN.

The network 1218 embodied as a cellular network may utilize a mobile telecommunications technology such as, but not limited to, GSM, UMTS, CDMA ONE, CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, and greater generation mobile telecommunications technologies. In addition, mobile data communications technologies such as GPRS, EDGE, the HSPA protocol family including HSDPA, EUL or otherwise termed HSUPA, HSPA+, and various other current and future mobile data communications technologies are contemplated for use by the network 1218. Therefore, the embodiments presented herein should not be construed as being limiting to a particular mobile telecommunications technology and/or standards utilizing such technologies.

Turning now to FIG. 13, an illustrative mobile device 1300 and components thereof will be described. In some embodiments, the mobile device 102 described above with reference to FIGS. 1 and 2 can be configured as and/or can have an architecture similar or identical to the mobile device 1300 described herein in FIG. 13. It should be understood, however, that the mobile device 102 may or may not include the functionality described herein with reference to FIG. 13. While connections are not shown between the various components illustrated in FIG. 13, it should be understood that some, none, or all of the components illustrated in FIG. 13 can be configured to interact with one another to carry out various device functions. In some embodiments, the components are arranged so as to communicate via one or more busses (not shown). Thus, it should be understood that FIG. 13 and the following description are intended to provide a general understanding of a suitable environment in which various aspects of embodiments can be implemented, and should not be construed as being limiting in any way.

As illustrated in FIG. 13, the mobile device 1300 can include a display 1302 for displaying data. According to various embodiments, the display 1302 can be configured to display network connection information, various graphical user interface (“GUI”) elements, text, images, video, virtual keypads and/or keyboards, messaging data, notification messages, metadata, Internet content, device status, time, date, calendar data, device preferences, map and location data, combinations thereof, and/or the like. The mobile device 1300 also can include a processor 1304 and a memory or other data storage device (“memory”) 1306. The processor 1304 can be configured to process data and/or can execute computer-executable instructions stored in the memory 1306. The computer-executable instructions executed by the processor 1304 can include, for example, an operating system 1308, one or more applications 1310, which may include the network connection manager 206, the network decision engine 208, other computer-executable instructions stored in the memory 1306, or the like. In some embodiments, the applications 1306 also can include a UI application (not illustrated in FIG. 13).

The UI application can interface with the operating system 1308, such as the operating system 204 shown in FIG. 2, to facilitate user interaction with functionality and/or data stored at the mobile device 1300 and/or stored elsewhere. In some embodiments, the operating system 1308 can include a member of the SYMBIAN OS family of operating systems from SYMBIAN LIMITED, a member of the WINDOWS MOBILE OS and/or WINDOWS PHONE OS families of operating systems from MICROSOFT CORPORATION, a member of the PALM WEBOS family of operating systems from HEWLETT PACKARD CORPORATION, a member of the BLACKBERRY OS family of operating systems from RESEARCH IN MOTION LIMITED, a member of the IOS family of operating systems from APPLE INC., a member of the ANDROID OS family of operating systems from GOOGLE INC., and/or other operating systems. These operating systems are merely illustrative of some contemplated operating systems that may be used in accordance with various embodiments of the concepts and technologies described herein and therefore should not be construed as being limiting in any way.

The UI application can be executed by the processor 1304 to aid a user in answering/initiating calls, data communications, entering/deleting data, entering and setting user IDs and passwords for device access, configuring settings, manipulating address book content and/or settings, multimode interaction, interacting with other applications 1310, and otherwise facilitating user interaction with the operating system 1308, the applications 1310, and/or other types or instances of data 1312 that can be stored at the mobile device 1300. The data 1312 can include, for example, cell-type information, load information, local device information, and/or other data described herein.

According to various embodiments, the applications 1310 can include, for example, presence applications, visual voice mail applications, messaging applications, text-to-speech and speech-to-text applications, add-ons, plug-ins, email applications, music applications, video applications, camera applications, location-based service applications, power conservation applications, game applications, productivity applications, entertainment applications, enterprise applications, combinations thereof, and the like. The applications 1310, the data 1312, and/or portions thereof can be stored in the memory 1306 and/or in a firmware 1314, and can be executed by the processor 1304. The firmware 1314 also can store code for execution during device power up and power down operations. It can be appreciated that the firmware 1314 can be stored in a volatile or non-volatile data storage device including, but not limited to, the memory 1306 and/or a portion thereof.

The mobile device 1300 also can include an input/output (“I/O”) interface 1316. The I/O interfaced 1316 can be configured to support the input/output of data such as location information, presence status information, user IDs, passwords, and application initiation (start-up) requests. In some embodiments, the I/O interface 1316 can include a hardwire connection such as a universal serial bus (“USB”) port, a mini-USB port, a micro-USB port, an audio jack, a PS2 port, an IEEE 1394 (“FIREWIRE”) port, a serial port, a parallel port, an Ethernet (RJ411) port, an RJ11 port, a proprietary port, combinations thereof, or the like. In some embodiments, the mobile device 1300 can be configured to synchronize with another device to transfer content to and/or from the mobile device 1300. In some embodiments, the mobile device 1300 can be configured to receive updates to one or more of the applications 1310 via the I/O interface 1316, though this is not necessarily the case. In some embodiments, the I/O interface 1316 accepts I/O devices such as keyboards, keypads, mice, interface tethers, printers, plotters, external storage, touch/multi-touch screens, touch pads, trackballs, joysticks, microphones, remote control devices, displays, projectors, medical equipment (e.g., stethoscopes, heart monitors, and other health metric monitors), modems, routers, external power sources, docking stations, combinations thereof, and the like. It should be appreciated that the I/O interface 1316 may be used for communications between the mobile device 1300 and a network device or local device.

The mobile device 1300 also can include a communications component 1318. The communications component 1318 can be configured to interface with the processor 1304 to facilitate wired and/or wireless communications with one or more networks such as the RANs 104 described herein. In some embodiments, other networks include networks that utilize non-cellular wireless technologies such as WI-FI or WIMAX. In some embodiments, the communications component 1318 includes a multimode communications subsystem for facilitating communications via the cellular network and one or more other networks.

The communications component 1318, in some embodiments, includes one or more transceivers. The one or more transceivers, if included, can be configured to communicate over the same and/or different wireless technology standards with respect to one another. For example, in some embodiments one or more of the transceivers of the communications component 1318 may be configured to communicate using GSM, CDMAONE, CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, and greater generation technology standards. Moreover, the communications component 1318 may facilitate communications over various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, TDMA, FDMA, W-CDMA, OFDM, SDMA, and the like.

In addition, the communications component 1318 may facilitate data communications using GPRS, EDGE, the HSPA protocol family including HSDPA, EUL or otherwise termed HSUPA, HSPA+, and various other current and future wireless data access standards. In the illustrated embodiment, the communications component 1318 can include a first transceiver (“TxRx”) 1320A that can operate in a first communications mode (e.g., GSM). The communications component 1318 also can include an N^(th) transceiver (“TxRx”) 1320N that can operate in a second communications mode relative to the first transceiver 1320A (e.g., UMTS). While two transceivers 1320A-N (hereinafter collectively and/or generically referred to as “transceivers 1320”) are shown in FIG. 13, it should be appreciated that less than two, two, and/or more than two transceivers 1320 can be included in the communications component 1318.

The communications component 1318 also can include an alternative transceiver (“Alt TxRx”) 1322 for supporting other types and/or standards of communications. According to various contemplated embodiments, the alternative transceiver 1322 can communicate using various communications technologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared, infrared data association (“IRDA”), near field communications (“NFC”), other RF technologies, combinations thereof, and the like. In some embodiments, the communications component 1318 also can facilitate reception from terrestrial radio networks, digital satellite radio networks, internet-based radio service networks, combinations thereof, and the like. The communications component 1318 can process data from a network such as the Internet, an intranet, a broadband network, a WI-FI hotspot, an Internet service provider (“ISP”), a digital subscriber line (“DSL”) provider, a broadband provider, combinations thereof, or the like.

The mobile device 1300 also can include one or more sensors 1324. The sensors 1324 can include temperature sensors, light sensors, air quality sensors, movement sensors, accelerometers, magnetometers, gyroscopes, infrared sensors, orientation sensors, noise sensors, microphones proximity sensors, combinations thereof, and/or the like. Additionally, audio capabilities for the mobile device 1300 may be provided by an audio I/O component 1326. The audio I/O component 1326 of the mobile device 1300 can include one or more speakers for the output of audio signals, one or more microphones for the collection and/or input of audio signals, and/or other audio input and/or output devices.

The illustrated mobile device 1300 also can include a subscriber identity module (“SIM”) system 1328. The SIM system 1328 can include a universal SIM (“USIM”), a universal integrated circuit card (“UICC”) and/or other identity devices. The SIM system 1328 can include and/or can be connected to or inserted into an interface such as a slot interface 1330. In some embodiments, the slot interface 1330 can be configured to accept insertion of other identity cards or modules for accessing various types of networks. Additionally, or alternatively, the slot interface 1330 can be configured to accept multiple subscriber identity cards. Because other devices and/or modules for identifying users and/or the mobile device 1300 are contemplated, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.

The mobile device 1300 also can include an image capture and processing system 1332 (“image system”). The image system 1332 can be configured to capture or otherwise obtain photos, videos, and/or other visual information. As such, the image system 1332 can include cameras, lenses, charge-coupled devices (“CCDs”), combinations thereof, or the like. The mobile device 1300 may also include a video system 1334. The video system 1334 can be configured to capture, process, record, modify, and/or store video content. Photos and videos obtained using the image system 1332 and the video system 1334, respectively, may be added as message content to an MMS message, email message, and sent to another mobile device. The video and/or photo content also can be shared with other devices via various types of data transfers via wired and/or wireless communication devices as described herein.

The mobile device 1300 also can include one or more location components 1336. The location components 1336 can be configured to send and/or receive signals to determine a geographic location of the mobile device 1300. According to various embodiments, the location components 1336 can send and/or receive signals from global positioning system (“GPS”) devices, assisted-GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellular network triangulation data, combinations thereof, and the like. The location component 1336 also can be configured to communicate with the communications component 1318 to retrieve triangulation data for determining a location of the mobile device 1300. In some embodiments, the location component 1336 can interface with cellular network nodes, telephone lines, satellites, location transmitters and/or beacons, wireless network transmitters and receivers, combinations thereof, and the like. In some embodiments, the location component 1336 can include and/or can communicate with one or more of the sensors 1324 such as a compass, an accelerometer, and/or a gyroscope to determine the orientation of the mobile device 1300. Using the location component 1336, the mobile device 1300 can generate and/or receive data to identify its geographic location, or to transmit data used by other devices to determine the location of the mobile device 1300. The location component 1336 may include multiple components for determining the location and/or orientation of the mobile device 1300.

The illustrated mobile device 1300 also can include a power source 1338. The power source 1338 can include one or more batteries, power supplies, power cells, and/or other power subsystems including alternating current (“AC”) and/or direct current (“DC”) power devices. The power source 1338 also can interface with an external power system or charging equipment via a power I/O component 1340. Because the mobile device 1300 can include additional and/or alternative components, the above embodiment should be understood as being illustrative of one possible operating environment for various embodiments of the concepts and technologies described herein. The described embodiment of the mobile device 1300 is illustrative, and should not be construed as being limiting in any way.

As used herein, communication media includes computer-executable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics changed or set in a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.

By way of example, and not limitation, computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-executable instructions, data structures, program modules, or other data. For example, computer media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the mobile device 1300 or other devices or computers described herein, such as the computer system 1200 described above with reference to FIG. 12. For purposes of the claims, the phrase “computer-readable storage medium” and variations thereof, does not include waves, signals, and/or other transitory and/or intangible communication media, per se. In an illustrative embodiment, a computer-readable storage medium is a tangible computer-readable storage medium.

Encoding the software modules presented herein also may transform the physical structure of the computer-readable media presented herein. The specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to, the technology used to implement the computer-readable media, whether the computer-readable media is characterized as primary or secondary storage, and the like. For example, if the computer-readable media is implemented as semiconductor-based memory, the software disclosed herein may be encoded on the computer-readable media by transforming the physical state of the semiconductor memory. For example, the software may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. The software also may transform the physical state of such components in order to store data thereupon.

As another example, the computer-readable media disclosed herein may be implemented using magnetic or optical technology. In such implementations, the software presented herein may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations also may include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.

In light of the above, it should be appreciated that many types of physical transformations may take place in the mobile device 1300 in order to store and execute the software components presented herein. It is also contemplated that the mobile device 1300 may not include all of the components shown in FIG. 13, may include other components that are not explicitly shown in FIG. 13, or may utilize an architecture completely different than that shown in FIG. 13.

Based on the foregoing, it should be appreciated that concepts and technologies for device-based idle mode load balancing been disclosed herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological and transformative acts, specific computing machinery, and computer-readable media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the claims.

The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the subject disclosure. 

We claim:
 1. A mobile device comprising: a processor; and a memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising receiving a cell information message comprising load information of a current camping cell on which the mobile device is currently camping, and load information of a neighbor cell of a plurality of neighbor cells to the current camping cell, obtaining cell-type information of the current camping cell, obtaining cell-type information of the neighbor cell, determining a mobility state of the mobile device, and based upon the load information of the current camping cell, the load information of the neighbor cell, the cell-type information of the current camping cell, the cell-type information of the neighbor cell, and the mobility state information, selecting a target camping cell.
 2. The mobile device of claim 1, wherein the current camping cell operates within a first frequency band and the neighbor cell operates within at least a second frequency band, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the first frequency band and at least the second frequency band.
 3. The mobile device of claim 2, wherein the current camping cell and the neighbor cell are each logical cells operating within a same physical cell.
 4. The mobile device of claim 1, wherein the current camping cell operates in accordance with a first radio access technology and the neighbor cell operates in accordance with at least a second radio access technology, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the first radio access technology and at least the second radio access technology.
 5. The mobile device of claim 4, wherein the current camping cell and the neighbor cell are each logical cells operating within a same physical cell.
 6. The mobile device of claim 1, wherein the memory further comprises computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising receiving WI-FI load information from a WI-FI access point, and wherein selecting the target camping cell comprises selecting the target camping cell or the WI-FI access point further based upon the WI-FI load information.
 7. The mobile device of claim 1, wherein the memory further comprises computer-executable instructions that, when executed by the processor, cause the processor to perform an operation comprising determining a received signal strength of the current camping cell and a received signal strength of the neighbor cell, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the signal strength of the current camping cell and the signal strength of the neighbor cell.
 8. A computer-readable storage medium comprising computer-executable instructions that, when executed by a processor of a mobile device, cause the processor to perform operations comprising: receiving a cell information message comprising load information of a current camping cell on which the mobile device is currently camping, and load information of a neighbor cell of a plurality of neighbor cells to the current camping cell; obtaining cell-type information of the current camping cell; obtaining cell-type information of the neighbor cell; determining a mobility state of the mobile device; and based upon the load information of the current camping cell, the load information of the neighbor cell, the cell-type information of the current camping cell, the cell-type information of the neighbor cell, and the mobility state information, selecting a target camping cell.
 9. The computer-readable storage medium of claim 8, wherein the current camping cell operates within a first frequency band and the neighbor cell operates within at least a second frequency band, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the first frequency band and at least the second frequency band.
 10. The computer-readable storage medium of claim 9, wherein the current camping cell and the neighbor cell are each logical cells operating within a same physical cell.
 11. The computer-readable storage medium of claim 8, wherein the current camping cell operates in accordance with a first radio access technology and the neighbor cell operates in accordance with at least a second radio access technology, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the first radio access technology and at least the second radio access technology.
 12. The computer-readable storage medium of claim 11, wherein the current camping cell and the neighbor cell are each logical cells operating within a same physical cell.
 13. The computer-readable storage medium of claim 8, further comprising computer-executable instructions that, when executed by the processor, cause the processor to perform an operation comprising receiving WI-FI load information from a WI-FI access point, and wherein selecting the target camping cell comprises selecting the target camping cell or the WI-FI access point further based upon the WI-FI load information.
 14. The computer-readable storage medium of claim 8, further comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising determining a received signal strength of the current camping cell and a received signal strength of the neighbor cell, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the signal strength of the current camping cell and the signal strength of the neighbor cell.
 15. A method comprising: receiving, at a mobile device, a cell information message comprising load information of a current camping cell on which the mobile device is currently camping, and load information of a neighbor cell of a plurality of neighbor cells to the current camping cell; obtaining cell-type information of the current camping cell; obtaining cell-type information of the neighbor cell; determining, by the mobile device, a mobility state of the mobile device; and based upon the load information of the current camping cell, the load information of the neighbor cell, the cell-type information of the current camping cell, the cell-type information of the neighbor cell, and the mobility state information, selecting, by the mobile device, a target camping cell.
 16. The method of claim 15, wherein the current camping cell operates within a first frequency band and the neighbor cell operates within at least a second frequency band, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the first frequency band and at least the second frequency band.
 17. The method of claim 16, wherein the current camping cell and the neighbor cell are each logical cells operating within a same physical cell.
 18. The method of claim 15, wherein the current camping cell operates in accordance with a first radio access technology and the at least one neighbor cell operates in accordance with at least a second radio access technology, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the first radio access technology and at least the second radio access technology.
 19. The method of claim 15, further comprising receiving WI-FI load information from a WI-FI access point, and wherein selecting the target camping cell comprises selecting the target camping cell or the WI-FI access point further based upon the WI-FI load information.
 20. The method of claim 15, further comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising determining a received signal strength of the current camping cell and a received signal strength of the neighbor cell, and wherein selecting the target camping cell comprises selecting the target camping cell further based upon the signal strength of the current camping cell and the signal strength of the neighbor cell. 